Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2038

reference
79-tree-1
name
2038
tree-preservation-order

undefined

79-tpo-1
uprn
address-text
point
POINT (-1.019871 50.880300)
geometry
MULTIPOLYGON (((-1.019815 50.880294,-1.019817 50.880305,-1.019825 50.880315,-1.019837 50.880323,-1.019853 50.880328,-1.019871 50.880330,-1.019888 50.880328,-1.019904 50.880324,-1.019917 50.880316,-1.019925 50.880306,-1.019928 50.880295,-1.019926 50.880283,-1.019918 50.880273,-1.019906 50.880265,-1.019890 50.880260,-1.019872 50.880258,-1.019855 50.880260,-1.019839 50.880265,-1.019826 50.880273,-1.019818 50.880283,-1.019815 50.880294)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL